Night Owl 6

home *** CD-ROM | disk | FTP | other *** search

/ Night Owl 6 / Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso / 033a / vbbs530.zip / NETGUIDE.DOC < prev next >

Wrap

Text File | 1991-11-06 | 25KB | 593 lines

▒▒▄ ▒▒▄ ▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▄ ▒▒▄ ▒▒▒▒▒▒▄ ▒▒▄ ▒▒█ ▒▒█ ▒▒█ ▒▒█▀▒▒█ ▀▒▒█▀▀ ▒▒█ ▒▒█ ▒▒█▀▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒█▀ ▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒▒█ ▒▒█ ▒▒▒▒█▀ ▒▒█ ▒▒█▀▒▒▄ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█▀ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒▒▄ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀▀▀▀▀ ▀▀ ▀▀ ▀▀▀▀▀▀ ▒▒▒▄▄ ▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒█▒▒█▒▒█ ▒▒█▀▀▀▀ ▀▒▒█▀▀ ▒▒█ ▀▒▒▒█ ▒▒▒▒▒▄ ▒▒█ ▒▒█ ▒▒█ ▒▒█▀▀▀ ▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒▒▄ ▒▒█ ▀▀ ▀▀ ▀▀▀▀▀▀ ▀▀ The VirtualNET Guide ───────────────────────────────────────────────────────── - Table of Contents - About VirtualNET............................. 1 Network Message Areas........................ 1 The "Multi-Net".............................. 1 E-Mail....................................... 2 Multi-mail and CC:s.......................... 2 Networked File Listings...................... 3 Taglines..................................... 3 Joining VirtualNET........................... 4 The Role of the AC........................... 5 Establishing a Client-Server connect......... 6 Network Decorum.............................. 7 Network Support.............................. 7 The Future................................... 8 Appendix A................................. 9 Installing the Net...................... 9 Network Configuration................... 9 Appendix B................................. 10 VNET Command lines...................... 10 VNET Macros............................. 11 Network Files........................... 12 Log Files............................... Appendix C................................. VWW4 Utility............................ Setting up WWIVnet...................... Setting up WWIVLink..................... ────────────────────────────────────────────────────────── - 1 - -------------------- What is VirtualNET?: -------------------- VirtualNET is a wide area network of on-line bulletin board systems running the Virtual BBS software authored by Roland De Graaf. This fast growing network is free and open to all who wish to become a part of it. Friendly, fun, and non-political by nature, participation in VirtualNET is widely encouraged. Networked message areas, email and requestable networked filelistings are a few of the features which highlight network activity. ------------------------ Networked Message Areas: ------------------------ At the core of VirtualNET are 22 message areas known as Star Message Bases. These are the original "non-hosted" VirtualNET subs and are provided to you preconfigured in a DATABASE.CFG which you may edit (delete or add to) with the VBBS configuration software. Other subs (topic areas) are available for automatic request by a SysOp and are listed in the current VSUBSLST.TXT. Aside from the Star Message Bases, listed subs have informal "hosts". These hosts act as discussion leaders within a given message area and should be afforded some degree of courtesy in that regard. If a SysOp would like to "Host" a sub topic of his or her own, all that needs to be done is to contact the VirtualNET Subslist Coordinator 1@4080, provide a Formal Name for the sub with a brief description of it along with a request for a sub # assignment and inclusion into the next SUBSLiST.NET ---------------- The "Multi-Net": ---------------- The Muli-Net is inclusive of other Networks and allows Message areas and email to be gated presently among VirtualNET, WWIVnet, and WWIVLink. The multinet allows the "gating" of message bases and sub boards between networks. At the present time, Non hosted VirtualNET subs are themselves NOT being gated outside of the network. Hosted VirtualNET subs however may be gated as the "host" sees fit. To gate subs from other networks INTO VirtualNET, you must first obtain the permission of the Host of that Sub, and then request a Gateway sub type assignment from the VirtualNET Subslist Coordinator. To gate other networks between themselves, permission MUST be obtained from EACH sub or conference Host involved on those networks. - 2 - ------ Email: ------ Private email routing is a function of the network. Each user on your system has a unique VirtualNET address and if given appropriate security may send and recieve mail not only across VirtualNET but, also across the multinet (other networks). A user on any VirtualNET system may send email to a WWIVnet address for instance just by identifying the network name at the prompt after the user and node number (x@xxxx) is entered in the "To:" line. The mail is gated out to WWIVnet (or whatever network has been chosen) at the first "gate" it comes to as it is routed up the network. Conversely, a WWIVnet user may send mail to a VirtualNET user by directing it through a known email gateway. The main WWIV gateway routing address on VirtualNET is 2@6655. So, from a WWIVnet board, a WWIVnet user can send mail to a VirtualNET user like so; 1) address the mail to a WWIVnet gate 2@6655 (main VirtualNET gateway) 2) On the FIRST line of that email, address the person's VirtualNET address prefacing it with three "***". When the mail hits the gateway, the software will see that routing instruction and route the mail to the VirtualNET address. example: ***1@4080 Another Network feature of the email is attached files. Attached files may be sent to any address on VirtualNET by any user configured by the SysOp to do so. There is no limit on the size of the file which can be attached to an email. For that reason, you will probably want to limit the access of this feature. ------------------- Multi-mail and CCs: ------------------- A unique and powerful feature of the VBBS/NET software is Multimail. This enables a SysOp and those with appropriate security levels as defined by the SysOp to maintain up to 9 seperate mailing lists, each with the ability to store an unlimited number of local and Network addresses which span the multinet. This INCLUDES the ability to CC: or multimail attached files this way as well. CC:s are seperately definable to user security and as multimail, there is no limit on the number of addresses that can be Carbon Copied at any given time. Note on Multimail Usage: VirtualNET considers itself a Guest of the networks within the Multinet. Each VirtualNET sysop has the responsibility to conduct themselves in a way which is becoming of that "guest" status. Arbitrary use of the CC or Multimail function is strongly discouraged. - 3 - ------------------------ Networked File Listings: ------------------------ Along with Email and the Message Bases, VirtualNET features a the actual networking of FILES. Through an automated request system (functional but still in development), VirtualNET SysOps, by configuring their VBBS program to do so, may recieve File listings from networked directories across the network (see appendix for installation notes). These file listings appear on your system as downloadable files only, similar to <offline> listings, they are marked as <Network File>. By pressing "R", a user may reqest a networked file. The request is then sent to the SysOp for approval or disapproval. If approved, the request is then automatically sent to the SysOp of the originating board where that SysOp will A)pprove or D)issaprove the request. If the request is approved, the file is then sent. Once this system becomes polished, each VirtualNET board will be able to display File listings that may very well represent Hundreds and perhaps thousands of Megabytes of files on their system. --------- Taglines: --------- Taglines are a great way to provide a personal and informative "stamp" on your messages to advertise your system and it's features. In your VBBS directory is a file called TAGLINE.1. This is your system's network "tag line" that is stamped at the bottom of the outgoing messages from your board. This file can be either edited with a std Ascii editor, or as well using an Ansi Draw program. You can have as many as 999 different system taglines (.1 thru .999) If you use an Ansi tagline, it should be block saved limiting it to 80 columns. Although there is no specific policy on the use of networked taglines within VirtualNET, SysOps should be mindful of two things; first, that within the Multinet, subs which are a part of other networks, and perhaps other networks themselves may have policy regarding the use of taglines. If you carry "gated" subs or are part of another network, it is recommended that you familiarize yourself with policy related to tagline usage. Secondly, keep in mind that "monster" ansi taglines are significantly larger than simple Ascii tags. A new feature in VBBS 5.30 is the ability to turn taglines off, as is required by some of the sub hosts from other networks (tagline= 0 in DATABASE.CFG). - 4 - ------------------- Joining VirtualNET: ------------------- Included with the VBBS 5.30 program, is a list of VirtualNET BBSs which is current at the time of the 5.30 release (BBSLIST.NET). If you would like to have your BBS join VirtualNET or have further questions regarding VirtualNET, please contact the Area Coordinator (AC) for your area as listed in the BBSLIST.NET. If your area does not yet have an AC, please contact one of the two VirtualNET Regional Coordinators (RC) as listed. Both RCs can be reached through VirtualNET or WWIVnet addresses; RC (east) The Dutch Ghetto (Snoop) 1@6160 VirtualNET 1@6659 WWIVnet RC (west) The Lemurian Co-op (Cat In The Hat) 1@9160 VirtualNET 1@9699 WWIVnet There are many Area Coordinator positions not yet assigned and available. Should you desire to be the AC for your area, please let the RC know this in your node request email. Whether you are sending a node request to your AC or an RC, please use following format: Turning in a new node request: Board Name ____________ Sysop Name ____________ BBS Phone # (XXX)-XXX-XXXX Voice Phone# (XXX)-XXX-XXXX Max Baud Rate supported_________ Modem type (2400, /HST COMPUCOM, DS, V.32 etc..) Connect to: @xxxx (if known) Other Network affiliation (if any)____________________ Node requests are usually effected within a weeks time. Generally, you can expect to become official within a few days of your application. Updates to the BBSLIST.NET and CONNECT.NET files are sent out each Sunday evening reflecting additions and changes for the 7 days preceding. - 5 - ------------------- The Role of the AC: ------------------- (ACs) - At the backbone of VirtualNET are the Area Coordinators. Normally, one AC is assigned to each telephone area code. This position is purely voluntary. If an Area code has no AC, then the position will generally be offered to each VirtualNET SysOp succesively IN that area as they join the network. Requirements of the VirtualNET AC- 1) Be opperating an accessable VBBS 24 hours per day. 2) Be able and willing to provide time and effort toward support and the growth of the network. Duties of the VirtualNET ACs- 1) Promote and support VBBS/NET within your area as you are able. Encourage and help others to be a part of, and contributors to VirtualNET. 2) Provide a positive image of VirtualNET within the online community. 3) Resolve conflicts that arise when able within the area and promote harmonious participation within the network. 4) Active participation in the VirtualNET AC sub. VirtualNET does NOT exclude anyone. There is NO basis for a denial or delay of VirtualNET node assignments EXCEPT at the Network Coordinator level. If an AC feels he or she has reason to suspect that a pending new network node should be denied a VirtualNET node number, that sysop should contact the NC or a Regional Coordinator directly. Connects are purely voluntary. An AC is encouraged, but not required to provide a connect for a VirtualNET system. An AC should ofcourse help a new VirtualNET node locate a suitable connect. VirtualNET is a FREE and OPEN network. It is non-exlusive by nature and is NOT hierarchal in the manner of many other networks. Often times, an AC might want to name an assistant AC to help particularly in the event that the AC is going to be inaccessable for any length of time. AC's are each assigned 10 VirtualNET subs for area specific use. ACs are highly encouraged to set up a netted SysOps sub for VirtualNET SysOps in their area. - 6 - -------------------------------------------- Establishing Connects (Servers and Clients): -------------------------------------------- Normally, at the same time that a node number is assigned, a connect is established between the new node and a "Server". The stucture of the network is currently that of a "Hub". The main Server is located in Western Michigan using a US Robotics HST and the network branches out from that area. It is desirable for a node to make a local connect when possible. If there is currently more than one VirtualNET board in your area, consideration to become a "Client" of that system should be primary. Often, a local dialing area will name one system as the Server and divide the monthly networking costs by the number of BBSs in the local system. If there is not yet another VirtualNET BBS in your area, one of the two VirtualNET Regional Coordinators will help you in establishing the best connect for your board. Note: Once your Network account has been established, it is incumbant upon you as a Client to NET in to your Server in a timely manner. Due to matters regarding storage of Network Packets, Clients who do not NET in to their server for 7 days run the risk of having their pending packet deleted by the Server SysOp. If you are having problems, or for whatever reason are not able to recieve your packet from your Server on a timely basis, be sure to contact your Server right away. Also, if you are going to be leaving the network, please notify your Server as well as your Area Coordinator. -------------- The Subs List: -------------- The VirtualNET Subs List is updated weekly, and made available for network file request. AC's are encouraged to provide the subslist for local downloading. By default, a VirtualNET DATABASE.CFG containing the 22 VirtualNET "Star" Message bases, the 4 SysOp/Support subs, the VirtualNET "Scripts & Mods" Networked File listing dir (899) and a Network File request dir to recieve any files requested by you from the network. Other subs are available to you by automated request. You simply need to add each sub you would like to recieve to your database.cfg. The subs come to you automatically and do not require that you request them from anyone. Once subscribing to a new sub however, it is common practice to announce your board's presence in that message area. Any questions regarding VirtualNET subs or Requests to either Host a VirtualNET sub or Gate a sub from another network need to be directed to the VirtualNET Subslist Coordinator (1@4080 Friday Jones). There is no limitation on the number of subs a sysop may host nor limitation of the sub content. Neither VirtualNET nor it's Network Coordinator endorse or maintain formal affiliation in any way to the subs hosted by the network sysops. Although VirtualNET maintains no responsibility to the activity of it's SysOps, illegal activity is expressly forbidden within the network. It is expected that VirtualNET SysOps will act in a responsible manner. Any networked BBS known to be engaging in activity which is not legal will be dropped from the subslist. - 7 - -------- Decorum: -------- VirtualNET has been fortunate to date in not having to deal with an issue of a Network user creating problems for others. As we grow however, it is inevitable that a situation will arize which requires remedy. First and Foremost, it is a SysOp's unique responsibilty to limit Network access on his or her system to responsible users. SysOps are expected to handle any problem user which is accessing the network from his or her board. In the event that a problem is persistant, a warning will be issued to that system. If the problem continues, the Network Coordinator will have no choice other than to suspend the network connect to the originating node. -------- Support: -------- Sometimes things don't work quite as they should when first establishing a connect with a server. If you have read and followed the documentation, and find that you are for whatever reason recieving errors, contact your Server and let him or her know what the problem is. VBBS and VirtualNET share the same cooperative support structure. Servers, AC's and CORE support boards are there to help you should you experience problems. The email that you send regarding problems should always include your Network address (node #), as well as your name, software version, WHICH network you're having problems with, and whether you are a running the program Standalone or as a door. It is important as well that you are as specific as possible regarding the nature of the problem as well as where it occurs. Invariably, almost all errors are the result of something not being quite right in the installation. The Support structure available to you is geared for maximum efficiency in resolving problems. No matter who you contact, your mail has a good chance of being forwarded within the support structure to another SysOp for resolution. This way, not only is the volume of support spread more evenly, but as well should result in a more prompt and accurate reply to the SysOp requiring support. If you have access to the VirtualNET Support Subs however, please make use of the public support by posting there as it will provide the greatest benifit to the Net as a whole. - 8 - ----------- The Future: ----------- The future of VirtualNET is heavily bound to the present. VirtualNET has the current distiction of being the fastest growing privately run network in the nation. With effort on the part of all pioneering VirtualNET SysOps, VirtualNET will continue to grow at an exponential rate. The future of the network software will see a continued efficiency of design. Added networked features can expect to see an inclusion of the FIDO format into the Multinet among other things. The Networked Filelistings and request system can expect to see some polishing soon, and a Virtual Offline Mail Reader which interacts directly with the VNET EXE is something to look forward to in the very near future. -= * =- - 9 - ----------- Appendix A: - N E T W O R K I N S T A L L A T I O N - ----------- In order to use the networking features, you will need to have the following programs: (Which VBBS will utilize automatically.) DSZ DSZ External Protocol Driver PKZIP and PKUNZIP PKware ZIP Archive Utilities Installing the Net- -------------------- The VirtualNET networking software, VNET.EXE is already included with the VBBS program. Once you have recieved you node assignment and have established yourself as a "client" to a VirtualNET "server" you simply need to do setup the NETWORK section in Vconfig. To do this, you enter your node number #### in the NETWORK.CFG. As well, you need to insert your Server node # and Phone #. Events and Dialing Thresholds ------------------------------- *********************************************************** *************OKAY ZARG, TAKE IT FROM HERE****************** *********************************************************** - 10 - ------------ Appendix B : ------------ Appendix B................................. VNET Command lines...................... Network Files........................... VNET Macros............................. Log Files............................... VNET.EXE is the networking software for the Virtual BBS/NET. It should be run out of the same directory as your Virtual BBS. For the most part, VBBS.EXE activates VNET.EXE as needed, however there are command switches which you may employ during execution from a batchfile or Dos prompt. The syntax for VNET.EXE is: VNET <command-switch> <command-switch> tells VNET what to do, the possibilities are: /NET - This command does a network callout to your designated host. Upon completion, it exits back to DOS. /HOST - This option tells VNET.EXE that a VirtualNET system has called in, and that its time to do an "answering-system" net transfer. /DIAL - This options lets a "Server" call to a "Client" system. (Sort of the reverse of /NET) Usage: VNET /DIAL5150 will dial a client @5150 /UPDATE - Updates all the mail packets. (also "/U") /ANALYZE - Analyzes VirtualNET connect and bbslist information sent to you from the Network Coordinator. Example: VNET /ANALYZE /Z - Used to unpack any pending .PKT files Example: VNET /Z #### (where #### is the node # preceding the .PKT extention) /$ - Used to List, review and delete VirtualNET posts after bundling into Net Packets (similar to LNET in WWIVnet). - 11 - ------------ VNET Macros: ------------ VBBS has a new and unique ability of Vnet.exe to employ the use of macros in establishing a Net connection with another VBBS system. If you are running VBBS from a matrix logon or as a door within another system, you now have the ability to serve as a VirtualNET HOST system to other boards from WITHIN the matrix logon or BBS door. If you are already the host to a remote VirtualNET system which is running in a matrix logon or door, you may now connect to that system for polling or whatever. The macro supports 3 commands. All 3 commands are 4 characters long, and 1 space is expected between the command and its arguement. RECV Waits for a string of characters. If they don't show up within 30 seconds, the call is aborted. SEND Sends a string of characters. WAIT Tells the macro facility what the boards [PAUSE] string is, so that it can be handled should it come up when RECV is waiting for its string. If it pops up, the macro facility automatically sends a 0x0D. The use of this facility is optional. A WWIV example: WAIT [PAUSE] RECV NN: SEND Acct name^m RECV PW: SEND codeword^m RECV ###-###- SEND 0000^m RECV T - SEND . RECV ? SEND 1 The above example logs on to a WWIV board, and runs door # 1. Note that you may send and recv control characters by putting a ^ in front of them. When the macro is done executing, VNET.EXE proceeds immediately to waiting for the ° which should pop up when VBBS starts running as a door. - 12 - Appendix C................................. VWW4 Utility............................ Setting up WWIVnet...................... Setting up WWIVLink..................... WWIVnet-- VBBS is able to directly access WWIVnet. Registered SysOps will be given the VWW4.EXE which will enable the full use of the WWIVnet networking software from within VBBS. A particularly notable feature of running WWIVnet inside of VBBS is that VBBS is able to carry an UNLIMITED number of Network subs. VBBS can even act as a WWIVnet SERVER! VirtualNET is a gateway to WWIVnet. That is a VBBS user has the unique ability to access WWIVnet mail, as well as any gated subs being carried by your board. In order to gate a WWIVnet sub into VirtualNET, you simply need to assign it a VirtualNET networked sub number in addition to it's WWIVnet sub type. -=-=-=-=-=-=-=-=-=-=-=- VirtualNET Guide ver 5.30 by Cat In The Hat